Programmable small form-factor pluggable module

ABSTRACT

A small form factor pluggable (“SFP”) transceiver for use in a communications network includes a transmitter adapted to be coupled to the network for supplying signals to the network, a receiver adapted to be coupled to the network for receiving signals from the network, and a programmable signal processing module coupled to the transmitter and the receiver and adapted to be programmed from a remote station coupled to the network. The module can be programmed to perform at least one service or management function on the network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/176,966, filed Oct. 31, 2018, now allowed, which is a continuation of U.S. patent application Ser. No. 15/645,482, filed Jul. 10, 2017, now U.S. Pat. No. 10,135,537, which is a continuation of U.S. patent application Ser. No. 13/551,804, filed Jul. 18, 2012, now U.S. Pat. No. 9,735,874, which incorporates by reference in their entireties the following applications, all of which have the same filing date of Jul. 18, 2012: U.S. Pat. No. 8,830,869, “Systems and Methods of Detecting and Assigning IP Addresses to Devices with ARP Requests,” by Robitaille and Lemieux; U.S. Pat. No. 9,106,706, “Systems and Methods of Using Beacon Messages to Discover Devices Across Subnets,” by Robitaille and Bouffard; U.S. Pat. No. 8,751,615, “Systems and Methods of Discovering and Controlling devices without Explicit Addressing,” by Robitaille and Bouffard, and U.S. Pat. No. 8,862,702, “Systems and Methods of Installing and Operating Devices without Explicit Network Addresses,” by Robitaille and Lemieux.

FIELD OF THE INVENTION

This invention is directed towards the use of an SFP for the purpose of offering Service OAM functions. For ease of deployment, the SFP can operate without any previous knowledge of the network where it is deployed and the behaviour of the SFP and the services it can offer can be managed in a centralized manner or distributed manner.

BACKGROUND OF THE INVENTION

An SFP is a compact, hot-pluggable transceiver used for both telecommunication and data communications applications. It generally interfaces a network device mother board (for a switch, router, media converter or similar device) to a fiber optic or copper networking cable. SFP transceivers are designed to support SONET, Gigabit Ethernet, Fibre Channel, and other communications standards. The following description is based on an optical SFP, but it should be understood to cover any type of SFPs.

SUMMARY OF THE INVENTION

In accordance with one embodiment, a small form factor pluggable (“SFP”) transceiver for use in a communications network includes a transmitter adapted to be coupled to the network for supplying signals to the network, a receiver adapted to be coupled to the network for receiving signals from the network, and a programmable signal processing module coupled to the transmitter and the receiver and adapted to be programmed from a remote station coupled to the network, the module being programmable to perform at least one service and management functions on the network. The programmable signal processing module may be a field programmable gate array or an application specific integrated circuit.

In specific implementations, the programmable signal processing module is programmable to perform at least one service assurance function on the network. such as monitoring network traffic and diagnosing issues (e.g., performing remote in-service Layer 1-4 loopback, ITU-T Y.1564 and RFC-2544 performance testing), and/or monitoring actual customer statistics from a web browser or portable test set. The programmable signal processing module may also be programmable to perform service management functions on the network, such as policing, traffic shaping and VLAN mapping.

The programmable signal processing module may be programmed to listen to traffic on the network, to detect a predetermined message broadcast by a remote device coupled to the network, and to respond to the predetermined message to indicate that the module is coupled to the network and is functioning. Communications with the remote device may be without the use of IP protocols over an ISO Layer 2 network.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by reference to the following description taken in conjunction with the accompanying drawings.

FIG. 1 is a diagrammatic illustration of an SFP optical transceiver.

FIG. 2 is a diagrammatic illustration of an SFP optical transceiver that includes an inline programmable module such as a FPGA.

FIG. 3 is a diagrammatic illustration of an adapter device that includes an SFP optical transceiver that further includes an inline programmable module such as a FPGA.

FIG. 4 is a diagrammatic illustration of a system in which an SFP optical transceiver located at a network node with an FPGA that is programmed from a remote node.

FIG. 5 is a diagrammatic illustration of a system similar to that of FIG. 4 in which the FPGA is configured as an embedded traffic generator.

FIG. 6 is a diagrammatic illustration of a system similar to that of FIG. 4 in which the FPGA is configured to perform intelligent loop back.

DETAILED DESCRIPTION OF ILLUSTRATED EMBODIMENTS

Although the invention will be described in connection with certain preferred embodiments, it will be understood that the invention is not limited to those particular embodiments. On the contrary, the invention is intended to cover all alternatives, modifications, and equivalent arrangements as may be included within the spirit and scope of the invention as defined by the appended claims.

Turning now to the drawings and referring first to FIG. 1, an SFP optical transceiver module 100 houses an optical transmitter 101 and an optical receiver 102, as per FIG. 1. The optical transmitter 101 generally comprises components for generating an optical signal (e.g., a light source, such as a light-emitting diode (LED) or laser diode) and one or more optics elements for directing the light into the end of a transmit optical fiber. The optical receiver 102 generally comprises the components for receiving an optical signal (e.g., a photodetector or photosensor) and one or more optics elements for directing light output from the end of a receive optical fiber onto the photodetector or photosensor. The optics elements of the transmitter and receiver of the module are part of an optics assembly 103 that couples to a duplex receptacle. There is also an electrical interface 104 that includes connections to provide power, ground and signals to the SFP. Although these modules have some rudimentary monitoring capability (e.g., 12C) that are generally limited to the physical characteristics such as power, they are by nature limited to the local physical link. These modules do not have the diagnostic capabilities that are required to identify and isolate network issues, such as delay or loss spanning the entire or a portion of the network.

FIG. 2 illustrates an optical SFP transceiver module 200 that is the same as the module 100 with the addition of a Field Programmable Gate Array (FPGA) 205. The FPGA can be added to the SFP housing, either inline as depicted in FIG. 2, or as an adaptor device. FIG. 3 depicts an where the adaptor device 301 that contains an FPGA 302 and an SFP 303 and plugs into a port 304.

Additional power and a power converter may be added to the SFP to feed the FPGA. The FPGA may initially contain some programming, but can also be configured and/or re-programmed from a remote station or node without requiring changes to the software on the network node where the SFP with the FPGA resides. The FPGA can also be operated remotely from a remote station or node. The FPGA may be replaced with other programmable modules such as ASIC-based solutions.

Since the objective is to manage the FPGA remotely without having to modify the software or firmware on the node it resides, there is a need for discovering that the SFP housing an FPGA has been connected on the network.

In one embodiment, the FPGA on the SFP is programmed to perform service assurance functions on the network, such as monitoring network traffic and diagnosing issues, performing remote, in-service Layer 1-4 loopback, ITU-T Y.1564 and RFC-2544 performance testing, I-way delay and jitter measurements, and monitoring actual customer statistics from a web-browser or portable test set without the need of any other test equipment, loopback testing, service management and demarcation. The FPGA can also be programmed to perform service management functions such as policing, traffic shaping, VLAN mapping etc.

If power consumption on the SFP is an issue, the unit can be configured with a subset of the functionality that complies with the power limitations. The set of features can be reprogrammed remotely on an as-needed basis without affecting the node or taking the port out of service. For example, using different FPGA loads, the on-board storage can support multiple such loads. Loads with lesser functions can run at lower clock speed and therefore consume less power, or they may simply have less logic active at a time. Other techniques for increasing the efficiency of a load that are known in the art can also be applied.

The FPGA can be configured remotely while the port is active. After proper identification of the remote programming node, to prevent security breach, the FPGA collects and assembles configuration packets into binary files, checks the integrity of the files, and then reprograms itself.

FIG. 4 illustrates an embodiment in which a node 401 is configured with several standard SFP ports 404 and one SFP port 402 with a programmable FPGA 403. All the ports 402 and 404 are connected to one or more networks 405 using a respective link 406. The FPGA 403 is discovered and configured and optionally programmed remotely by a node 407 using a control path 408.

FIG. 5 illustrates an embodiment in which a node 501 is configured with several standard SFP ports 504 and one SFP port 502 with a programmable FPGA 503. All the ports 502, 504 are connected to one or more networks 505 using a respective link 506. The FPGA 503 is discovered and configured and optionally programmed remotely by a node 507 using a control path 508. In this case, the FPGA is configured as an embedded traffic generator 510 to create test packets 509 for insertion in the paths of the standard SFPs 504. In this case, the port hosting the FPGA 502 may be a normal forwarding port, or it could be only used to house a test traffic generator.

Referring to FIG. 6, in another embodiment, a node 601 is configured with several standard SFP ports 604 and one SFP port 602 with a programmable FPGA 603. All the ports 602, 604 are connected to one or more networks 605 using a respective link 606. The FPGA 603 is discovered and configured and optionally programmed remotely by a node 607 using a control path 608. In this case, the FPGA is configured to perform intelligent loop back 610 by swapping MAC and IP addresses and returning the packets in the paths 609 of the standard SFPs 604. In this case, the port hosting the FPGA 602 may be a normal forwarding port or it could be only used to house the device providing loop back capability.

The FPGA or other programmable module can be discovered in the network using a discoverer (e.g. testing unit, router, remote node) that is local to the subnet where the programmed module is located. The module to be discovered is programmed to watch for responses of a device located upstream.

The FPGA or other programmable module can be reprogrammed remotely to perform other functions or services. A discoverer can transmit a management packet to the FPGA or other programmable module to request that it loads different firmware or program logic from local permanent storage or from a remote location. This is achieved by virtue of a dual-stage boot method. When the FPGA or other programmable module needs to load new firmware or program logic, it will indicate this in permanent storage (for instance a FLASH memory) and/or special hardware register to guide the primary boot loader where to locate the secondary boot.

The present invention includes systems having processors to provide various functionality to process information, and to determine results based on inputs. Generally, the processing may be achieved with a combination of hardware and software elements. The hardware aspects may include combinations of operatively coupled hardware components including microprocessors, logical circuitry, communication/networking ports, digital filters, memory, or logical circuitry. The processors may be adapted to perform operations specified by a computer-executable code, which may be stored on a computer readable medium.

The steps of the methods described herein may be achieved via an appropriate programmable processing device, such as an external conventional computer or an on-board field programmable gate array (FPGA) or digital signal processor (DSP), that executes software, or stored instructions. In general, physical processors and/or machines employed by embodiments of the present invention for any processing or evaluation may include one or more networked or non-networked general purpose computer systems, microprocessors, field programmable gate arrays (FPGA's), digital signal processors (DSP's), micro-controllers, and the like, programmed according to the teachings of the exemplary embodiments of the present invention, as is appreciated by those skilled in the computer and software arts. Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the exemplary embodiments, as is appreciated by those skilled in the software arts. In addition, the devices and subsystems of the exemplary embodiments can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as is appreciated by those skilled in the electrical arts. Thus, the exemplary embodiments are not limited to any specific combination of hardware circuitry and/or software.

Stored on any one or on a combination of computer readable media, the exemplary embodiments of the present invention may include software for controlling the devices and subsystems of the exemplary embodiments, for driving the devices and subsystems of the exemplary embodiments, for processing data and signals, for enabling the devices and subsystems of the exemplary embodiments to interact with a human user, and the like. Such software can include, but is not limited to, device drivers, firmware, operating systems, development tools, applications software, and the like. Such computer readable media further can include the computer program product of an embodiment of the present invention for performing all or a portion (if processing is distributed) of the processing performed in implementations. Computer code devices of the exemplary embodiments of the present invention can include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, and the like. Moreover, parts of the processing of the exemplary embodiments of the present invention can be distributed for better performance, reliability, cost, and the like.

Common forms of computer-readable media may include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD-ROM, CDRW, DVD, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other suitable memory chip or cartridge, a carrier wave or any other suitable medium from which a computer can read.

While particular embodiments and applications of the present invention have been illustrated and described, it is to be understood that the invention is not limited to the precise construction and compositions disclosed herein and that various modifications, changes, and variations may be apparent from the foregoing descriptions without departing from the spirit and scope of the invention as defined in the appended claims. 

1. A system to remotely program a small form factor pluggable optical transceiver (SFP) located at a network node, the system comprising: a programmable processor coupled with the SFP; a discoverer and a remote station coupled to the SFP via the network; the discoverer discovering the programmable processor; and the remote station remotely programming the programmable processor.
 2. The system of claim 1, wherein remotely programming comprises downloading one or more service assurance functions to be performed by the SFP.
 3. The system of claim 2, in which the at least one service assurance function is selected from a group consisting of: (i) monitoring network traffic and diagnosing network traffic issues, (ii) performing remote in-service Layer 1-4 loopback, (iii) ITU-T Y.1564 and RFC-2544 performance testing, and (iv) monitoring actual customer statistics from a web browser or portable test set.
 4. The system of claim 1, wherein the programmable processor detects a remotely broadcast predetermined message.
 5. The SFP of claim 1, wherein the programmable processor responds to a predetermined message to indicate that the programmable processing module is coupled to the network and is functioning.
 6. The SFP of claim 1, wherein the discoverer transmits a management packet to the programmable processor to request programming.
 7. The SFP of claim 1, further comprising a plurality of standard SFP ports coupled to the network, wherein the remote station programs the programmable processor to generate one or more test packets to insert in one or more network paths of the plurality of standard SFP ports.
 8. The SFP of claim 1, wherein the discoverer is co-located with the remote station.
 9. A method to remotely program a small form factor pluggable optical transceiver (SFP) located at a network node, the method comprising: discovering a programmable processor coupled with the SFP; and remotely programming the programmable processor.
 10. The method of claim 9, wherein remotely programming comprises downloading one or more service assurance functions to be performed by the SFP.
 11. The method of claim 10, in which the at least one service assurance function is selected from a group consisting of: (v) monitoring network traffic and diagnosing network traffic issues, (vi) performing remote in-service Layer 1-4 loopback, (vii) ITU-T Y.1564 and RFC-2544 performance testing, and (viii) monitoring actual customer statistics from a web browser or portable test set.
 12. The method of claim 9, wherein the programmable processor detects a remotely broadcast predetermined message.
 13. The method of claim 9, wherein the programmable processor responds to a predetermined message to indicate that the programmable processing module is coupled to the network and is functioning.
 14. The method of claim 9, wherein the discoverer transmits a management packet to the programmable processor to request programming.
 15. The method of claim 9, further comprising programming the programmable processor to generate one or more test packets to insert in one or more network paths of a plurality of standard SFP ports. 